fix(core): cap session shell output - #45136
Conversation
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
The following comment was made by an LLM, it may be inaccurate: Potential duplicate found:
Recommendation: Check if PR #45109 already implements the 50 KiB capping logic or if these PRs address complementary aspects of the same issue (#45099). |
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
Issue for this PR
Closes #45099
Type of change
What does this PR do?
Session shell commands use the same 50 KiB preview limit as regular shell output. Large command output remains file-backed for paging, while the model-facing session history receives only the bounded preview.
The conflict resolution keeps the current V2 session refactor and applies the shared limit at the relocated session-shell capture point.
How did you verify your code works?
Screenshots / recordings
Not applicable.
Checklist